Update Release Plan according to Sync26#47
Draft
albertoramosmonagas wants to merge 1 commit intomainfrom
Draft
Conversation
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
This PR updates the repository release plan for the Sync26 meta-release.
It aligns the
release-plan.yamlwith the next CAMARA release cycle by:Sync26This is needed so the repository is correctly tracked by the Release Management automation and remains consistent with the current CAMARA release planning process.
Which issue(s) this PR fixes:
Fixes #39
Special notes for reviewers:
Please review this PR from a release planning perspective.
This change does not modify API behavior or implementation. It only updates the repository release declaration so it is correctly aligned with the Sync26 planning cycle and Release Management tooling.
Changelog input
Additional documentation
This section can be blank.